Controlling wireless transition timers based on application and content

ABSTRACT

Wireless transition timers associated with wireless transition states are adaptively controlled in relation to use of applications by user equipment (UE). A UE can include a transition management component (TMC) that can adaptively control wireless transition timers associated with wireless states based on application type, session content, or other factors. The TMC monitors data flow associated with an application and, for a current or subsequent communication session, controls the length of wireless transition timers and switching between wireless states to improve UE, application, and/or network performance while maintaining QOE for the user. The TMC can access a timer look-up table that maps wireless transition timers to application type, content type, user behavior, or other factors. The TMC also can desirably control maintaining persistence or always-on connections by controlling switching between wireless states using the adapted wireless transition timers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 15/011,378, filed Jan. 29, 2016, andentitled “CONTROLLING WIRELESS TRANSITION TIMERS BASED ON APPLICATIONAND CONTENT,” which is a continuation of U.S. patent application Ser.No. 14/603,132 (now U.S. Pat. No. 9,282,517), filed Jan. 22, 2015, andentitled “CONTROLLING WIRELESS TRANSITION TIMERS BASED ON APPLICATIONAND CONTENT,” which is a continuation of U.S. patent application Ser.No. 13/662,915 (now U.S. Pat. No. 8,971,194), filed Oct. 29, 2012, andentitled “CONTROLLING WIRELESS TRANSITION TIMERS BASED ON APPLICATIONAND CONTENT,” the entireties of which applications are herebyincorporated herein by reference.

TECHNICAL FIELD

This disclosure relates generally to network communications, e.g., tocontrolling wireless transition timers based on application and content.

BACKGROUND

A wireless communication system can be utilized to provide wirelessaccess to various communication services (e.g., voice, video, data,messaging, content broadcast, etc.) for users of the system. Wirelesscommunication systems can operate according to a variety of networkspecifications and/or standards, such as, for example, Universal MobileTelecommunications System (UMTS), Third Generation Partnership Project(3GPP) Long Term Evolution (LTE), High Speed Packet Access (HSPA). Thesespecifications and/or standards use different modulation techniques,such as Code Division Multiple Access (CDMA), Time Division MultipleAccess (TDMA), Frequency Division Multiple Access (FDMA), Multi-CarrierCDMA (MC-CDMA), Single-Carrier CDMA (SC-CDMA), Orthogonal FrequencyDivision Multiple Access (OFDMA), Single-Carrier Frequency DivisionMultiple Access (SC-FDMA), and so on.

Communication devices (e.g., wireless communication devices), such asmobile phones, electronic tablets, electronic gaming devices, andcomputers, are increasingly using applications to perform variousfunctions and to communicate information between these communicationdevices and other communication devices (e.g., other mobile phones,electronic tablets, electronic gaming devices, computers, servers,etc.). An application can reside on a user's communication device, in acloud, and/or on a server farm, for example.

The above-described description is merely intended to provide acontextual overview of wireless communication networks, and is notintended to be exhaustive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example system that canadaptively control wireless transition timers associated with wirelessstates in relation to use of applications by user equipment (UE) in acommunication network, in accordance with various aspects andembodiments described herein.

FIG. 2 depicts a block diagram of another example system that canadaptively control wireless transition timers associated with wirelessstates in relation to use of applications by a UE in a communicationnetwork, in accordance with various aspects and embodiments.

FIG. 3 illustrates a diagram of an example system that can be employedto generate a mapping that can facilitate adaptively controllingwireless transition timers associated with wireless states in relationto use of applications by a UE in a communication network, in accordancewith various aspects and embodiments described herein.

FIG. 4 depicts a block diagram of an example transition managementcomponent in accordance with various aspects and embodiments of thedisclosed subject matter.

FIG. 5 presents a block diagram of an example communication network inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 6 depicts a block diagram of an example UE in accordance with anaspect of the disclosed subject matter.

FIG. 7 illustrates a block diagram of an example access point inaccordance with an aspect of the disclosed subject matter.

FIG. 8 illustrates a flow diagram of an example method for adaptivelycontrolling wireless transition timers associated with wireless statesin relation to use of applications by a UE in a communication network,in accordance with various aspects and embodiments.

FIG. 9 depicts a flow diagram of another example method for adaptivelycontrolling wireless transition timers associated with wireless statesin relation to use of applications by a UE in a communication network,in accordance with various aspects and embodiments.

FIG. 10 is a flow diagram of still another example method for generatinga mapping relating to wireless transition timers and wireless states tofacilitate adaptively controlling wireless transition timers associatedwith wireless states in relation to use of applications by a UE in acommunication network, in accordance with various aspects andembodiments.

FIG. 11 illustrates a flow diagram of an example method adaptivelycontrolling wireless transition timers associated with wireless statesand signaling in relation to use of applications by a UE in acommunication network to facilitate controlling resource usageassociated with the UE, in accordance with various aspects andembodiments.

FIG. 12 is a schematic block diagram illustrating a suitable operatingenvironment.

FIG. 13 is a schematic block diagram of a sample-computing environment.

DETAILED DESCRIPTION

Various aspects of the disclosed subject matter are now described withreference to the drawings, wherein like reference numerals are used torefer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of one or more aspects. It maybe evident, however, that such aspect(s) may be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form in order to facilitate describing one ormore aspects.

Techniques for controlling transition of a communication device betweenwireless states are presented herein. The disclosed subject matter caninclude a method that can comprise identifying, by a system including aprocessor, a wireless transition timer based on information relating toactivity of an application and a wireless communication device. Themethod also can include controlling, by the system, switching of thewireless communication device between a first wireless state and asecond wireless state based on the wireless transition timer.

The disclosed subject matter also can include a system comprising amemory to store computer-executable instructions. The system also caninclude a processor, communicatively coupled to the memory, thatfacilitates execution of the computer-executable instructions to performoperations, comprising: determining a wireless transition timer based oninformation relating to activity of an application and a mobilecommunication device; and controlling transition of the mobilecommunication device between a first wireless state and a secondwireless state based on the wireless transition timer.

Further, the disclosed subject matter can include a computer-readablestorage device storing computer-executable instructions that, inresponse to execution, cause a system including a processor to performoperations. The operations can include identifying a wireless transitiontimer based on information relating to activity of an application and amobile communication device; and controlling transitioning of thewireless communication device between a first wireless state and asecond wireless state based on the wireless transition timer.

User equipment (UE) (e.g., wireless communication devices), such asmobile phones, electronic tablets, electronic gaming devices, andcomputers, can communicate with a communication network via a number ofdifferent types of communication channels having respectivecommunication functionality and consuming respective amounts of power.There can be a subset of communication channels comprising differentcommunication channels respectively associated with wireless states in asubset of available wireless states. For example, in accordance with aradio resource control (RRC) protocol (e.g., associated with UMTS),there can be four wireless states, including, e.g., an idle state, adedicated-channel state, a forward-access-channel state, and a pagingstate, that can be respectively associated with a non-connection andthree types of communication channels. In other implementations, therecan be more or less than four wireless states and/or different wirelessstates, and/or there can be more or less than three types ofcommunication channels, as well as the non-connection while in the idlestate.

When the UE is in the idle state, there can be no communicationconnection between the UE and the communication network, wherein theidle state can be associated with the lowest energy consumption relativeto the other wireless states. When the UE is in the dedicated-channel(DCH) state, there can be a dedicated communication connection (e.g.,CELL_DCH) that can provide for faster data transfer speeds than thecommunication connections associated with the other wireless states,wherein the DCH state can be associated with the highest amount ofenergy consumption relative to the other wireless states. When the UE isin a forward-access-channel (FACH) state, there can be a forward-accesschannel (e.g., CELL_FACH) established between the UE and thecommunication network, wherein the forward access channel can be acommon channel (as opposed to a dedicated channel) that can allow foruplink and downlink communication of data between the UE and thecommunication network at a lower transmission rate than that of thededicated channel, and wherein the FACH state can be associated with alower amount of energy consumption than that associated with the DCHstate, but a higher amount of energy consumption than that associatedwith the other wireless states. When the UE is in the paging state(e.g., URA paging state), there can be a paging channel (URA_PCH)established between the UE and the communication network, wherein thepaging channel can be a non-dedicated channel that can allow fordownlink communication of data between the UE and the communicationnetwork at a lower transmission rate than that of the forward-accesschannel, and wherein the paging state can be associated with a loweramount of energy consumption than that associated with the FACH state,but a higher amount of energy consumption than that associated with theidle state.

UEs are increasingly using applications, including intelligentapplications, to communicate information between these UEs and othercommunication devices (e.g., other mobile phones, electronic tablets,electronic gaming devices, computers, servers, etc.). An application canreside on a user's UE, in a cloud, and/or on a server farm, for example.

In wireless communication networks, management of wireless communicationchannels and states, network traffic, and network congestion can bedesirable to facilitate efficient communication of traffic between UEsand other communication devices. The increased use of applications byUEs, increase in the amount of traffic being communicated incommunication networks, increase in the volume of signaling incommunication networks (e.g., by repeated communication between UEs andthe network, and persistence or always-on communication connectionsassociated with UEs), differences in the classifications and/orcharacteristics of applications, continuing evolution of applications,and various other factors can make management of wireless communicationchannels and states, network traffic, and network congestionincreasingly more challenging and problematic for today's systems.Wireless state transition behavior, network behavior, and applicationbehavior can be dependent on a number of factors, such as, for example,type of application, type of content being communicated, the number ofactive users, network congestion level, user behavior with regard to UEsand applications, and/or the demographics of the user environments,including UE capabilities and the presence of other active applicationson the UEs.

For instance, streaming media (e.g., video content, audio content) ordata file downloads (e.g., downloads of songs, programs, videos, movies,etc.) by a UE can involve communication of a relatively large amount ofdata over a relatively short amount of time, while other types ofcommunications (e.g., retrieving a web page comprising textual data) bya UE can involve communication of a relatively smaller amount of dataand/or intermittent communication over a particular period of time. Asanother example, applications designed to be able to communicate via abroadband network can present a higher risk or problem to thecommunication network (e.g., mobile or cellular communication network)than applications designed specifically for mobile or lower speedcommunication networks. However, many of these applications (e.g.,applications designed for communication via a broadband network) mayfunction at an acceptable level in lower energy states (e.g., lowerenergy states associated with a Third Generation (3G) network, which cancomprise, for example, four wireless states), and these application canbe serviced by the communication network with a same or similar qualityof experience (QOE) while in a lower wireless state.

To that end, techniques for adaptively controlling wireless transitiontimers associated with wireless states in relation to use ofapplications by a UE are presented herein. A UE (e.g., mobile phones,electronic tablets, electronic gaming devices, computers, etc.) caninclude a transition management component that can adaptively controlwireless transition timers associated with wireless states based atleast in part on application type, session content, user behavior oractivity in relation to the application or UE, or other factors. Thetransition management component can use the adapted wireless transitiontimers to control switching of the UE between a one wireless state(e.g., higher power wireless state) and another wireless state (e.g., alower power wireless state) at desired (e.g., optimal, suitable, etc.)times to provide desired (e.g., optimal, enhanced, improved, etc.)performance. The transition management component can adapt wirelessstate transitions between different wireless states (e.g., Idle state,URA state, FACH state, DCH state, etc.) in accordance with thepredictive usage (e.g., predictive wireless resource usage) of theapplication.

The transition management component can generate a mapping of anapplication's expected usage (e.g., predictive wireless resource usage)to lower-layer wireless state transitions (e.g., lower-layerLong-Term-Evolution (LTE) wireless state transitions). For instance, thetransition management component can generate a mapping of wirelessstates and/or respectively associated wireless transition timers toapplication type, content type, user behavior or activity in relation tothe application or UE, or other factors or parameters. The transitionmanagement component and its functions, features, and controls canoperate on the UE to facilitate providing cross-layer enhancement (e.g.,optimization) functions.

When a UE is using an application, the transition management componentcan monitor data flow associated with the application and trackapplication data flow or behavior (e.g., changes in data flow orbehavior), user behavior or activity, and/or other activity orparameters. The transition management component can analyze the trackedinformation to facilitate identifying desirable (e.g., improved,acceptable, efficient, optimal, etc.) wireless transition timers to useduring a communication session and/or updating the mapping. For acurrent or subsequent communication session, the transition managementcomponent can control (e.g., dynamically or automatically control oradapt) the length of wireless transition timers (or selection ofwireless transition timers of respective lengths) and switching betweenwireless states to enhance (e.g., improve, optimize, etc.) UE,application, and/or network performance while maintaining a desirableQOE for the user. The transition management component can maintain andaccess a timer look-up table (e.g., stored in a data store) that caninclude the mapping relating to wireless states and/or wirelesstransition timers. The transition management component can receiveupdates from the communication network or other sources, and/or cangenerate updates on its own (e.g., based on analysis of informationrelating to the tracking of application data flow or behavior, userbehavior or activity, and/or other activity or parameters), to update(e.g., improve, optimize, etc.) the mapping and/or the wirelesstransition timers associated with the mapping.

After the transition management component identifies an application(e.g., identifies an application type) being used by the UE and/orchanges in application behavior, the transition management component canaccess the timer look-up table, analyze the mapping, and identify asuitable (e.g., optimal, acceptable, etc.) wireless transition timer(s)to use while the UE is using the application, based at least in part onthe type of application, type of content associated with theapplication, user behavior, and/or other factors or parameters. Thetransition management component can implement the identified wirelesstransition timer(s) to facilitate controlling switching of the UEbetween wireless states at desired (e.g., optimal, acceptable, etc.)times during use of the application to facilitate enhancing UEperformance (e.g., reduce power consumption, reduce signaling withcommunication network, reduce use of radio resources, reduce use ofprocessing resources, etc.) and/or communication network performance(e.g., improve use of radio resources, reduce signaling between the UEand communication network, more efficiently use radio resources, reduceor improve use of processing resources, etc.).

Certain types of applications can use always-on communicationconnections, wherein an application can send a keep-alive messageperiodically (e.g., every 5 seconds or 10 seconds) to the communicationnetwork to facilitate maintaining the always-on connection with thenetwork. The transition management component can desirably (e.g.,optimally, acceptably, efficiently, etc.) control signaling (e.g.,sending of keep-alive messages) associated with an always-on connection,and/or activity reporting associated with a UE, between the UE and thecommunication network (e.g., cellular communication network) during acommunication session and can desirably (e.g., optimally, acceptably,efficiently, etc.) control switching between wireless transition statesusing adapted wireless transition timers. This can desirably maintainthe integrity of the always-on communication connection while alsoenhancing (e.g., improving, optimizing, reducing, etc.) use of networkresources (e.g., radio resources, processing resources, etc.) and UEresources (e.g., power resources, radio resources, processing resources,etc.). In some implementations, to facilitate desirably controllingswitching of the UE between wireless states during use of an applicationthat utilizes an always-on communication connection between the UE andthe communication network, the transition management component canmodify a current policy (e.g., network or application policy) forkeep-alive messages to an enhanced (e.g., improved) policy forkeep-alive messages that can be tailored by the transition managementcomponent based at least in part on type of application, data flow andbehavior associated with the application, type of content, user behaviorin relation to the application or UE, and/or other factors. Forinstance, the transition management component can desirably adjust(e.g., dynamically or automatically adjust) a keep-alive policy orkeep-alive emulation protocol associated with use of an application thatwould otherwise undesirably waste network and/or UE resources to anenhanced keep-alive policy or enhanced keep-alive emulation protocol toreduce or eliminate the wasting of network and/or UE resources inrelation to use of the application. For example, if the transitionmanagement component determines, based at least in part on applicationdata flow or behavior and/or user behavior or activity, that frequentsending (e.g., every 5 seconds) of keep-alive messages to thecommunication network is unnecessary and an inefficient use ofresources, the transition management component can control the sendingof keep-alive messages to the communication network to reduce thefrequency of sending keep-alive messages (e.g., send every 2 minutesinstead of every 5 seconds) to the communication network, while stillmaintaining the integrity of the always-on connection (e.g., while stillproviding a desirable (e.g., same or substantially the same) QOE to theuser).

In some implementations, the transition management component also candesirably control switching of the UE between wireless transition statesusing the adapted wireless transition timers to facilitate desirably(e.g., optimally, acceptably, etc.) maintaining the performance ofapplications for communication connections (e.g., a push, sessioncontinuity, or persistence communication connections) between a UE and awireless communication network (e.g., 3G, Fourth Generation (4G), Wi-Fi,etc.) during communication sessions (e.g., using WEB 2.0 push, sessioncontinuity, and/or persistence connections practices or protocols). Thetransition management component can receive (e.g., from thecommunication network) or generate a mapping of IP protocols tolower-layer wireless states based at least in part on type ofapplication being used, application data flow or behavior, type ofcontent associated with the application or communication session, userbehavior in relation to the application or content, and/or otherfactors. The transition management component can use the mappingassociated with the IP protocols to facilitate identifying or adaptingwireless transition timers that can control switching the UE betweenwireless states in a manner that efficiently uses UE and/or networkresources, while also maintaining desirable (e.g., acceptable, suitable,etc.) performance of the application (e.g., the user still has adesirable (e.g., same or substantially the same) QOE when using theapplication with the adapted wireless transition timers as the userwould have had if the wireless transition timers had not been adapted orset by the transition management component).

For example, the transition management component can identify and applya first subset of wireless transition timers associated with wirelessstates for a UE using a first type of application (e.g., a voice over IP(VoIP) application) during a first communication session. The transitionmanagement component also can identify and apply a second (e.g.,different) subset of wireless transition timers associated with wirelessstates for the UE using a second type of application (e.g.,video-streaming application, or a web browser application) during asecond communication session, wherein the respective wireless transitiontimes of the first subset of wireless transition timers and secondsubset of wireless transition timers can be enhanced (e.g., optimized,improved, etc.) by the transition management component to facilitateenhancing UE performance and/or communication network performance.

Referring now to the drawings, FIG. 1 illustrates a block diagram of anexample system 100 that can adaptively control wireless transitiontimers associated with wireless states in relation to use ofapplications by a UE in a communication network, in accordance withvarious aspects and embodiments described herein. The system 100 cancomprise a UE 102 (e.g., mobile and/or wireless communication device,such as a mobile phone (e.g., 3GPP Universal Mobile TelecommunicationsSystem (UMTS) phone), electronic notebook, electronic pad or tablet,electronic gaming device, personal digital assistant (PDA), computer,set-top box, etc.) that can operate and communicate in a communicationnetwork environment. In an aspect, the UE 102 can be communicativelyconnected via a wireless communication connection(s) via an access point(AP) 104 to a communication network(s) 106.

In an aspect, as the UE 102 is moved through a wireless communicationnetwork environment, at various times, the UE 102 can be connected(e.g., wirelessly connected) to one of a plurality of APs (e.g., macroor cellular AP, femto AP, pico AP, Wi-Fi AP, Wi-Max AP, hotspot (e.g.,Hotspot 1.x, Hotspot 2.x, where x is an integer number; UE 102functioning as a mobile hotspot; etc.), etc.), such as an AP 104, thatcan operate in the wireless communication network environment. An AP(e.g., 104) can serve a specified coverage area to facilitatecommunication by the UE 102 or other UEs in the wireless communicationnetwork environment. The AP 104 can serve a respective coverage cell(e.g., macrocell, femtocell, picocell, etc.) that can cover a respectivespecified area, and the AP 104 can service mobile wireless devices, suchas UE 102, located in the respective area covered by the respectivecell, where such coverage can be achieved via a wireless link (e.g.,uplink (UL), downlink (DL)). When an attachment attempt is successful,the UE 102 can be served by the AP 104 and incoming voice and datatraffic can be paged and routed to the UE 102 through the AP 104, andoutgoing voice and data traffic from the UE 102 can be paged and routedthrough the AP 104 to other communication devices (e.g., another UE) inthe communication network environment. In an aspect, the UE 102 can beconnected and can communicate wirelessly using virtually any desiredwireless technology, including, for example, cellular, Wi-Fi, Wi-Max,wireless local area networks (WLAN), etc.

In another aspect, the communication network 106 can facilitate wirelessconnection with the UE 102 connected to the AP 104 and facilitatecommunication by or between a UE 102 and another UE(s) or other type ofcommunication device(s) (e.g., computer, server or server farm that caninclude an application server or content server that can be providevideo content, audio content, and/or other content comprising othertypes of information, etc.), such as communication device 108 associatedwith a first application 110 and communication device 112 associatedwith a second application 114, wherein the communication device 108 andcommunication device 112 each can be associated with (e.g.,communicatively connected to) the communication network 106 in thecommunication network environment.

An application being used by the UE 102 reside on the UE 102 or on aremote communication device (e.g., communication device 108,communication device 112), and/or can have functions that can beexecuted by the UE 102 and/or by another communication device (e.g.,communication device 108, communication device 112) associated with theapplication (e.g., first application 110, second application 114). Anapplication can be, for example, a mobile-to-mobile (M2M) type ofapplication, a VoIP type of application, or a near real time (NRT) typeof application, among other types of applications. In someimplementations, the UE 102 can be connected (e.g., directly) with oneor more applications (e.g., first application 110, second application114) using, for example, one or more various types of wirelesscommunication technology, such as near field communication (NFC)technology, Bluetooth technology, ZigBee technology, etc. In certainimplementations, the UE 102 can function as a mobile hotspot (e.g., AP)to which one or more applications can be wirelessly connected tofacilitate communication of traffic (e.g., voice or data traffic)between an application(s) 112 and the communication network 106 via theUE 102. It is to be further appreciated and understood that one or morecommunication devices (e.g., communication device 108, communicationdevice 112) can be located within a cloud, wherein, for example, thecloud can include a server farm comprising one or more servers (e.g.,application servers) that can be utilized to perform respectiveapplication functions (e.g., VoIP, video streaming, messaging,multimedia, electronic gaming, news-related functions, social mediafunctions, finance-related functions, etc.) based at least in part onthe type of application.

The communication network 106 can include one or more wireline networksand one or more wireless networks, wherein the one or more wirelessnetworks can be based on one or more various types of communicationtechnology or protocols, such as, for example, 3G, 4G, or x Generation(xG) network, where x can be virtually any desired integer or realvalue; Wi-Fi; etc. The communication network 106 (e.g., a core network,or a network comprising a core network and/or an IP-based network) canfacilitate routing voice and data communications between a communicationdevice(s) (e.g., UE 102) and other communication devices (e.g., anotherUE, communication device 108, communication device 112) associated withthe communication network 106 in the communication network environment.The communication network 106 also can allocate resources to the UE 102or other UEs in the communication network 106, convert or enforceprotocols, establish and enforce Quality of Service (QoS) for the UEs(e.g., UE 102), provide applications or services in the communicationnetwork 106, translate signals, and/or perform other desired functionsto facilitate system interoperability and communication in thecommunication network 106 (e.g., wireless portion of the communicationnetwork 106 or wireline portion of the communication network 106). Thecommunication network 106 further can include desired components, suchas routers, nodes, switches, interfaces, controllers, etc., that canfacilitate communication of data between communication devices in thecommunication network environment.

In accordance with various implementations, the UE 102 can adaptivelycontrol wireless transition timers associated with wireless states inrelation to use of an application(s) (e.g., first application 110,second application 114) by the UE 102 to facilitate efficientlycontrolling switching between wireless states by the UE 102. The UE 102can include a transition management component 116 that can adaptivelycontrol wireless transition timers associated with wireless states basedat least in part on a type of application, application data flow orbehavior, session content (e.g., video content, audio content, textualcontent, etc.), user behavior or activity in relation to the applicationor UE 102, or other factors. For instance, the transition managementcomponent 116 can use the adapted wireless transition timers to controlswitching of the UE 102 between one wireless state (e.g., higher powerwireless state) and another wireless state (e.g., a lower power wirelessstate) at desired (e.g., optimal) times to provide desired (e.g.,optimal, enhanced, improved, etc.) performance by the UE 102 and/or thecommunication network 106. The transition management component 116 canadapt wireless state transitions between different wireless states(e.g., Idle state, URA state, FACH state, DCH state, etc.) in accordancewith the predictive usage (e.g., predictive wireless resource usage) ofthe application (e.g., first application 110, second application 114).For example, a certain M2M application may have resource usagespecifications such that the M2M application can be suitably serviced byusing lower power wireless states, such as the FACH state or URA statewithout having to transition the UE 102 to the higher power DCH state.Based at least in part on this information (which can be reflected inthe mapping relating to wireless state transitions), the transitionmanagement component 116 can control switching of the UE 102 and use ofwireless transition timers to switch the UE 102 between the variouslower power wireless states (e.g., FACH state, URA state, idle state) atdesired times (e.g., in accordance with the adapted wireless transitiontimers) without transitioning the UE 102 to the higher power DCH state.It is to be appreciated and understood that, while the disclosed subjectmatter describes wireless states, such as DCH state, FACH state, URAstate, and idle state, in accordance with various implementations, thedisclosed subject matter can be used with various other types ofwireless states associated with various other types of wireless (e.g.,radio) state transition protocols.

The transition management component 116 can generate a mapping of anapplication's expected usage (e.g., predictive wireless resource usage)to lower-layer wireless state transitions (e.g., LTE wireless statetransitions). For instance, the transition management component 116 cangenerate a mapping of wireless states and/or respectively associatedwireless transition timers to type of application, data flow or behavior(e.g., changes in data flow or behavior) associated with theapplication, type of content, user behavior or activity in relation tothe application or UE 102, or other factors or parameters. Thetransition management component 116 can use the mapping to facilitateidentifying desired (e.g., adapted) wireless transition timers for useduring a communication session involving the UE 102 and an application(e.g., first application 110 or second application 114), as more fullydisclosed herein. The transition management component 116 and itsfunctions, features, and controls can operate on the UE 102 tofacilitate providing cross-layer enhancement (e.g., optimization)functions.

When the UE 102 is using an application (e.g., first application 110 orsecond application 114), the transition management component 116 canmonitor, probe, and/or track data flow, behavior, and/or activityassociated with the application (e.g., 110 or 114) or the user. Thetransition management component 116 can analyze the information relatingto the tracked data flow, behavior, and/or activity associated with theapplication to facilitate identifying desirable (e.g., improved,acceptable, efficient, optimal, etc.) wireless transition timers to useduring a communication session and/or to updating the mapping. Withregard to updating of a mapping, the transition management component116, by tracking data flow, behavior, and/or activity associated withthe application or the user, can gain knowledge and learn about usage ofthe application, and can modify the mapping and adjust wirelesstransition timers, in accordance with applicable state-switching-controlcriterion (or corresponding rules).

For a current or subsequent communication session, based at least inpart on the information analysis and the mapping, the transitionmanagement component 116 can control (e.g., dynamically or automaticallycontrol or adapt) the length of wireless transition timers (or selectionof wireless transition timers of respective lengths) and switchingbetween wireless states to enhance (e.g., improve, optimize, etc.) UE,application, and/or network performance, while maintaining a desirableQOE for the user of the UE 102. The transition management component 116can generate, maintain, and/or access a timer look-up table (e.g.,stored in a data store) that can include the mapping relating towireless states and/or associated wireless transition timers. Thetransition management component 116 can receive updates from thecommunication network 106 or other sources (e.g., communication device108, communication device 112), and/or can generate updates on its own(e.g., based at least in part on the analysis of tracked data flow,behavior, and/or activity associated with the application or user), toupdate the mapping and/or the wireless transition timers associated withthe mapping. The transition management component 116 can therefore beprogrammable and adaptable to suitably respond to different types ofapplications, changes in application behavior or data flow, changes inuser behavior or activity, etc.

After the transition management component 116 identifies an application(e.g., identifies an application type) being used by the UE, changes inapplication data flow or behavior, type of content associated with thecommunication session, etc., the transition management component 116 canaccess the timer look-up table, can analyze the mapping in relation tothe application, and/or changes in application data flow or behavior,type of content associated with the communication session, etc. From theanalysis of the mapping, the transition management component 116 canidentify a suitable (e.g., optimal, acceptable, etc.) wirelesstransition timer(s) to use while the UE 102 is using the application(e.g., first application 110 or second application 114), based at leastin part on the type of application (e.g., 110 or 114), data flow orbehavior associated with an application, type of content associated withthe application (e.g., 110 or 114), user behavior or activity (e.g.,current, recent, or historical user behavior or activity) in relation tothe application or UE 102, type of IP protocol, and/or other factors orparameters. The transition management component 116 can implement theidentified wireless transition timer(s) to facilitate controllingswitching of the UE 102 between wireless states (e.g., Idle state, URAstate, FACH state, DCH state, etc.) at desired (e.g., optimal,acceptable, etc.) times during use of the application (e.g., 110 or 114)to facilitate enhancing UE performance (e.g., reduce power consumption,reduce signaling between the UE 102 and the communication network 106,reduce use of radio resources by or processing resources on the UE 102,etc.) and/or communication network performance (e.g., improve use ofradio resources, reduce signaling between the UE 102 and communicationnetwork 106, reduce or improve use of processing resources, etc.).

For example, the transition management component 116 can identify andselect a first wireless transition timer to use for a first wirelessstate based at least in part on the mapping and information relating tothe type of application, application data flow or behavior, type ofcontent associated with the application, user behavior or activity inrelation to the application or UE 102, and/or other factors orparameters. While the UE 102 is in a first wireless state (e.g., DCHstate), the transition management component 116 can monitor activity onthe first communication connection or channel (e.g., Cell_DCH) and afirst wireless transition timer can be used to facilitate to determiningwhether to transition the UE 102 from the first wireless state to asecond wireless state (e.g., FACH state). If the transition managementcomponent 116 determines that there has been no activity or low activityon the first communication connection or channel for a period of timethat indicates the amount of time of the first wireless transition timerhas elapsed, the transition management component 116 can determine thatthe UE 102 is to be transitioned from the first wireless state to thesecond wireless state (e.g., FACH state). The transition managementcomponent 116 can transition the UE 102 from the first wireless state tothe second wireless state, and the UE 102 can switch from the firstcommunication connection or channel (e.g., Cell_DCH) to a secondcommunication connection or channel (e.g., Cell_FACH).

In some implementations, based at least in part on an analysis oridentification of an application (e.g., 110 or 114), application dataflow or behavior, content, user behavior, etc., associated with a UE102, the transition management component 116 can identify an instance(s)where a wireless transition timer may indicate that the wireless statefor a UE is to transition from a first wireless state (e.g., a higherpower wireless state, such as the DCH state) to a second wireless state(e.g., a relatively lower power wireless state, such as the FACH stateor Idle state), but can have information that can indicate the UE 102will be or is expected to be switched back to the first wireless statewithin a relatively short period of time that would render switchingback and forth between the first wireless state and second wirelessstate by the UE 102 inefficient as compared to maintaining the UE 102 inthe first wireless state. In such instance(s), the transition managementcomponent 116 can control the wireless transition timers and/ortransition of the UE 102 between wireless states to maintain the UE 102in the first wireless state, instead of switching the UE 102 from thefirst wireless state to the second wireless state and back to the firstwireless state again.

Certain types of applications can use always-on communicationconnections, wherein an application can send a keep-alive messageperiodically (e.g., every 5 seconds or 10 seconds) to the communicationnetwork to facilitate maintaining the always-on connection between theUE 102 and the communication network 106. The transition managementcomponent 116 can desirably (e.g., optimally, acceptably, efficiently,etc.) control signaling (e.g., sending of keep-alive messages)associated with an always-on connection, and/or activity reportingassociated with a UE 102, between the UE 102 and the communicationnetwork 106 (e.g., cellular communication network) during acommunication session and can desirably (e.g., optimally, acceptably,efficiently, etc.) control switching between wireless transition statesusing adapted wireless transition timers. This can desirably maintainthe integrity of the always-on communication connection while alsoenhancing (e.g., improving, optimizing, reducing, etc.) use of resources(e.g., radio resources, processing resources, etc.) of the communicationnetwork 106 and resources (e.g., power resources, radio resources,processing resources, etc.) of the UE 102. In some implementations, tofacilitate desirably controlling switching of the UE between wirelessstates during use of an application that utilizes an always-oncommunication connection between the UE 102 and the communicationnetwork 106, the transition management component 116 can modify acurrent policy (e.g., network or application policy) for keep-alivemessages to an enhanced policy for keep-alive messages that can betailored by the transition management component 116 based at least inpart on type of application (e.g., first application 110 or secondapplication 114), data flow and behavior associated with theapplication, type of content, user behavior or activity in relation tothe application (e.g., 110 or 114) or the UE 102, and/or other factors.For instance, the transition management component 116 can desirablyadjust (e.g., dynamically or automatically adjust) a keep-alive policyor keep-alive emulation protocol associated with use of an application(e.g., 110 or 114) that would otherwise undesirably waste network and/orUE resources to an enhanced keep-alive policy or enhanced keep-aliveemulation protocol to reduce or eliminate the wasting of network and/orUE resources in relation to use of the application (e.g., 110 or 114).

For example, the UE 102 can use an application (e.g., 110) that can bean email application that can use an always-on connection to maintainnear real-time updates or receipts for email being sent to the UE 102 orassociated UE user. The application (e.g., 110) can use a standardpractice or protocol for maintaining the always-on connection betweenthe UE 102 and the communication network 106 by transmitting akeep-alive message at a standard frequency (e.g., every 5 seconds). As aresult of this standard practice or protocol, when the application isused by the UE 102, the sending of keep-alive messages at the standardfrequency can result in the UE 102 always staying in the DCH state,which can cause the UE 102 to use a relatively significant amount ofpower, signaling (e.g., from the significant amount of sending ofkeep-alive messages), radio resources, and processing resources. Sendingthe keep-alive messages at the standard frequency may be acceptable ifthe UE user receives a lot of emails per hour and/or desires (e.g.,needs) to be notified of newly received emails as soon as possible.However, sending the keep-alive messages at this standard frequency canbe unacceptable and can result in an inefficient use of resources if theUE user does not receive a lot of emails per hour and/or does not desire(e.g., need) to be immediately notified of newly received emails.

The transition management component 116 can control signaling associatedwith the always-on connection and switching of the UE 102 betweenwireless states (e.g., using adapted wireless transition timers) toimprove the efficiency of the UE 102 while using the application (e.g.,110), while maintaining the integrity of the always-on connection andperformance of the application (e.g., while still providing a desirable(e.g., same or substantially the same) QOE to the user). For instance,the transition management component 116 can analyze data relating totracked data flow, behavior, and/or activity associated with theapplication (e.g., 110) or the user. The transition management component116 can identify that the user does not receive emails very frequently(e.g., approximately one email per hour on average) and the user doesnot check his emails that frequently (e.g., checks email every few hourson average). Based at least in part on the analysis results andapplicable state-switching-control criterion (or corresponding rules),the transition management component 116 can determine that the frequentsending (e.g., every 5 seconds) of keep-alive messages to thecommunication network 106 in accordance with the standard practice orprotocol is unnecessary and an inefficient use of resources. In responseto that determination, the transition management component 116 canidentify an enhanced practice, policy, or protocol that can modify(e.g., reduce) the frequency of sending of keep-alive messages from theUE 102 to the communication network 106 and identify desired wirelesstransition timers to control switching of the UE 102 to have the UE 102switch to a lower power and lower resource using state (e.g., idlestate) at desired times, and to switch up to the higher power, higherresource state (e.g., DCH state) at certain periodic times to facilitatereceiving information relating to emails (e.g., email notifications,emails, etc.), instead of maintaining a constant always-on connectionbetween the UE 102 and the communication network 106. For instance, inaccordance with the enhanced practice, policy, or protocol, thetransition management component 116 can control the sending ofkeep-alive messages from the UE 102 to the communication network 106 toreduce the frequency of sending keep-alive messages (e.g., to send akeep-alive message every 2 minutes instead of every 5 seconds) to thecommunication network 106, while still maintaining the integrity of thealways-on connection (e.g., while still providing a desirable (e.g.,same or substantially the same) QOE to the user). By reducing thefrequency of sending keep-alive messages and employing the desiredwireless transition timers, the transition management component 116 canmore efficiently control switching of the UE 102 to a lower power andlower resource using state (e.g., idle state) at desired times tofacilitate improving UE performance (e.g., reducing power consumption,reducing signaling between the UE 102 and the communication network 106,reducing use of radio resources by or processing resources on the UE102, etc.) and/or communication network performance (e.g., improving useof radio resources, reducing signaling between the UE 102 andcommunication network 106, reducing or improving use of processingresources, increasing statistical gain, etc.).

In accordance with various implementations, the transition managementcomponent 116 can control the sending of keep-alive messages from the UE102 to the communication network 106 by intercepting some of thekeep-alive messages and placing the intercepted messages in a queue forcontrolled release to the communication network 106 in accordance withthe modified frequency of the enhanced policy or discarding theintercepted messages, wherein the keep-alive messages that are notintercepted can be sent to the communication network 106 so that thefrequency of message sending is in accordance with the modifiedfrequency associated with the enhanced policy. In other implementations,where the application is an intelligent, adaptable, or programmableapplication, the transition management component 116 can send anotification or recommendation to the application (e.g., 110) to requestor instruct the application to modify its standard policy for sendingkeep-alive messages to correspond to the enhanced policy and reduce thefrequency of sending of keep-alive messages by the application.

In certain implementations, the transition management component 116 alsocan desirably (e.g., optimally, acceptably, etc.) control switching ofthe UE 102 between wireless transition states using wireless transitiontimers that can be adapted to facilitate desirably (e.g., optimally,acceptably, etc) maintaining the performance of applications forcommunication connections (e.g., a push, session continuity, orpersistence communication connections) between a UE 102 and a wirelesscommunication network (e.g., 3G, 4G, Wi-Fi, etc.) during communicationsessions (e.g., using WEB 2.0 push, session continuity, and/orpersistence connections practices or protocols). The transitionmanagement component 116 can receive (e.g., from the communicationnetwork 106) or generate a mapping of IP protocols (e.g., transmissioncontrol protocol (TCP)/IP, user datagram protocol (UDP), stream controltransmission protocol (SCTP), etc.) to lower-layer wireless states,wherein the mapping can be generated based at least in part on type ofapplication (e.g., 110 or 114) being used, application data flow orbehavior, type of content associated with the application (e.g., 110 or114) or communication session, user behavior or activity in relation tothe application (e.g., 110 or 114) or content, and/or other factors. Thetransition management component 116 can use the mapping associated withthe IP protocols to facilitate identifying or adapting wirelesstransition timers that can control switching the UE 102 between wirelessstates in a manner that can more efficiently use resources of the UE 102and/or resources of the communication network 106, while alsomaintaining desirable (e.g., acceptable, suitable, etc.) performance ofthe application (e.g., the user can still have a desirable (e.g., sameor substantially the same) QOE when using the application with theadapted wireless transition timers as the user would have had if thewireless transition timers had not been adapted or set by the transitionmanagement component 116).

For example, the transition management component 116 can identify andapply a first subset of wireless transition timers associated withwireless states for a UE 102 using a first type of application (e.g.,VoIP application, which, for example, can be the first application 110)during a first communication session, and identify and apply a second(e.g., different) subset of wireless transition timers associated withwireless states for the UE 102 using a second type of application (e.g.,video-streaming application, or a web browser application, which, forexample, can be the second application 114) during a secondcommunication session, wherein the respective wireless transition timesof the first subset of wireless transition timers and second subset ofwireless transition timers can be respectively enhanced (e.g.,optimized, improved, etc.) by the transition management component 116,based at least in part on the mapping, to facilitate enhancingperformance of the UE 102 and/or performance of the communicationnetwork 106.

Referring briefly to FIG. 2 (along with FIG. 1), FIG. 2 depicts adiagram of an example system 200 that can adaptively control wirelesstransition timers associated with wireless states in relation to use ofapplications by a UE in a communication network, in accordance withvarious aspects and embodiments described herein. The system 200 caninclude a transition management component 202 that can adaptivelycontrol wireless transition timers associated with wireless states basedat least in part on a type of application, changes in behavior orapplication data flow of the application, content (e.g., video content,audio content, textual content, etc.) associated with the communicationsession involving the application, user behavior or activity in relationto the application or the UE, or other factors. The transitionmanagement component 202 can be included in or associated with the UE.

The transition management component 202 can monitor or probe data flowassociated with applications used by the UE. There can be various typesof applications, such as, for example, VoIP applications 204, M2Mapplications 206, NRT applications 208, or other types of applications210. The transition management component 202 can generate a mapping ofwireless states and/or respectively associated wireless transitiontimers to type of application, application data flow or behavior, typeof content associated with the application, user behavior or activity inrelation to the application or UE, and/or other factors or parameters.The transition management component 202 can store that mapping in atimer look-up table 212. The wireless states can include, for example, aDCH state associated with Cell_DCH 214, a FACH state associated withCell_FACH 216, a paging state that can be associated with URA_PCH 218,and an idle state associated with idle 220 (e.g., no communicationconnection). There also can be a separate wireless state associated withCell PCH 222.

For a current or subsequent communication session, the transitionmanagement component 202 can access that mapping from the timer look-uptable and can utilize that mapping to facilitate controlling (e.g.,dynamically or automatically controlling or adapting) the length ofwireless transition timers (or selection of wireless transition timersof respective lengths) and switching between wireless states to enhance(e.g., improve, optimize, etc.) UE, application, and/or networkperformance while maintaining a desirable QOE for the user of the UE.For example, based at least in part on the mapping, the transitionmanagement component 202 can identify a first subset of wirelesstransition timers to use in relation to a first type of application(e.g., VoIP application 204) associated with a first type of content,and can use the first subset of wireless transition timers to controlswitching the UE between wireless states (e.g., DCH state, FACH state,paging state, and/or idle state) during the communication sessioninvolving the first type of application. Based at least in part on themapping, the transition management component 202 also can identify asecond subset of wireless transition timers to use in relation to afirst type of application (e.g., M2M application 206) associated with asecond type of content, and can use the second subset of wirelesstransition timers to control switching the UE between wireless statesduring the communication session involving the second type ofapplication. Based at least in part on the respective application types,application data flow or behavior, content types, or other factors ofthe first type of application and second type of application, asspecified in the mapping, the first subset of wireless transition timerscan be different from the second subset of wireless transition timers.

It is to be appreciated and understood that FIG. 2 depicts examplewireless transition times (e.g., 2-10 seconds (s)) and example bufferthresholds (e.g., RLC buffer threshold of 128-1024 bytes (B)), however,the disclosed subject matter is not so limited. For example, asdisclosed herein, the transition management component (e.g., 202) canadapt or adjust wireless transition timers based at least in part on thetype of application (e.g., VoIP application 204, M2M application 206,NRT application 208, etc.), data flow or behavior associated with anapplication, type of content associated with the application (e.g., 110or 114), user behavior or activity (e.g., current, recent, or historicaluser behavior or activity) in relation to the application or UE, type ofIP protocol, and/or other factors or parameters.

FIG. 3 illustrates a diagram of an example system 300 that can beemployed to generate a mapping that can facilitate adaptivelycontrolling wireless transition timers associated with wireless statesin relation to use of applications by a UE in a communication network,in accordance with various aspects and embodiments described herein. Thesystem 300 can include a UE 302 that can be associated with acommunication network (e.g., 106) via an AP (e.g., 104) in a wirelesscommunication network environment. The UE 302 can use variousapplications (e.g., first application 110, second application 114, etc.)at various times.

The UE 302 can include a transition management component 304 that canadaptively control wireless transition timers associated with wirelessstates of the UE 302 based at least in part on a type of application,session content (e.g., video content, audio content, textual content,etc.), user behavior or activity in relation to the application or UE302, and/or other factors.

When the UE 302 is using an application, the transition managementcomponent 304 can monitor data flow associated with the application and,for a current or subsequent communication session, can control (e.g.,dynamically or automatically control or adapt) the length of wirelesstransition timers (or selection of wireless transition timers ofrespective lengths) and switching between wireless states (e.g., Idlestate, URA state, FACH state, DCH state, etc.) to enhance (e.g.,improve, optimize, etc.) UE, application, and/or network performancewhile maintaining a desirable QOE for the user of the UE 302. Thetransition management component 304 can include a mapper component 306that can generate, maintain, and/or update a mapping 308 of anapplication's expected usage (e.g., predictive wireless resource usage)to lower-layer wireless state transitions (e.g., LTE wireless statetransitions). For instance, the mapper component 306 can generate,maintain, and/or update the mapping 308 of wireless states and/orrespectively associated wireless transition timers to type ofapplication, application data flow or behavior, type of content, userbehavior or activity in relation to the application or UE 302, type ofIP protocol, or other factors or parameters. The mapper component 306can store the mapping 308 in a timer look-up table 310, which can bestored in a data store 312.

The mapper component 306 can employ a desired mapper function 314 tofacilitate generating the mapping 308 in accordance with one or moredefined state-switching-control criterion and associated definedstate-switching-control protocol (and/or correspondingstate-switching-control rules) that can facilitate identification ofdesired wireless transition timers that can be used to adaptivelycontrol switching of the UE 302 between wireless states when using anapplication(s). The mapper component 306, using the mapper function 314,can generate, maintain, or update a mapping between the wirelesstransition timers and/or wireless states 316 and application (e.g., nameof application) and/or type of application 318, application (app.) dataflow and/or changes in application behavior 320, type of content 322,information associated with user behavior or activity in relation to anapplication or UE 302 and/or a user profile 324, IP protocols 326 (e.g.,associated with an IP-based communication network), and/or other factorsor parameters.

FIG. 4 depicts a block diagram of an example transition managementcomponent 400 in accordance with various aspects and embodiments of thedisclosed subject matter. The transition management component 400 can beemployed by a UE to facilitate adaptively controlling wirelesstransition timers associated with wireless states in relation to use ofapplications by the UE in a communication network, in accordance withvarious aspects and embodiments described herein.

The transition management component 400 can comprise a monitor component402 that can monitor or probe the behavior of the application data flowassociated with the application during a communication session involvingthe UE and the application. The monitor component 402 also can monitorwireless state transitions in relation to use of the application tofacilitate enhancing the timing of wireless state transitions during thecurrent or a subsequent communication session involving the UE and theapplication.

The transition management component 400 can include an aggregatorcomponent 404 that can aggregate data received (e.g., obtained) fromvarious entities (e.g., monitor component 402 or another component(s) ofthe transition management component 400, communication network,application, a server or other communication device, processor, datastore, etc.). The aggregator component 404 can correlate respectiveitems of data based at least in part on type of data (e.g., videocontent, audio content, textual data, metadata, etc.), application towhich the data relates, source of the data, time or date the data wasgenerated or received, etc., to facilitate analyzing of the data by theanalyzer component 406. For example, the aggregator component 404 canaggregate data relating to an application and/or other data (e.g., datarelating to the communication network) to facilitate generating amapping between wireless transition timers (and/or wireless states) andtype of application, type of content, user behavior or activity inrelation to the application or UE, and/or other factors or parameters.

The transition management component 400 can include the analyzercomponent 406, which can analyze data to facilitate identifying a typeof application, identifying a type of content, identifying applicationbehavior, identifying user behavior, identifying a suitable wirelesstransition timer to be implemented during a communication session thatinvolves the UE and the application, identifying a suitable wirelessstate for the UE to be in at a given time, generating a mapping relatingto wireless transition timers and wireless states, etc., and cangenerate analysis results, based at least in part on the data analysis.For example, the analyzer component 406 can analyze information relatingto the type of application, type of content associated with theapplication, user behavior or activity in relation to the application orUE, and/or the mapping related to the wireless transition timers andwireless states, and can generate analysis results that can facilitateidentifying a subset of wireless transition timers to use during acommunication session involving the UE and the application and/oridentifying a wireless state that the UE is to be in at a given timeduring the communication session.

The transition management component 400 also can comprise a statetransition component 408 that can identify a wireless state the UE is tobe in at a given time, and can control selecting or setting of wirelesstransition timers and transitioning the UE between various availablewireless states (e.g., Idle state, URA state, FACH state, DCH state,etc.) at respective times, based at least in part on the mappingrelating to wireless transition timers and wireless states, wherein themapping can be generated (e.g., by the mapper component 412) based atleast in part the type of application, application data flow orbehavior, type of content associated with the application, user behavioror activity in relation to the application or UE, type of IP protocol,and/or other factors or parameters, in accordance with one or moredefined state-switching-control criterion and associated definedstate-switching-control protocol (and/or correspondingstate-switching-control rules). The state transition component 408 canreceive analysis results from the analyzer component 406 to facilitatemaking decisions or determinations regarding wireless state transitionsand/or selection or setting of wireless transition timers for switchingthe UE between wireless states. The state transition component 408 alsocan control signaling between the UE and the communication network tofacilitate transition of the UE between different wireless states.

The transition management component 400 can include a timer component410 that can track an amount of time that has elapsed in relation to awireless transition timer being utilized by the transition managementcomponent 400 at a given time. The timer component 410 can signal thestate transition component 408 when the amount of time associated with awireless transition timer has elapsed to facilitate state transition bythe state transition component 408 from one wireless state to anotherwireless state.

The transition management component 400 can comprise a mapper component412 that can facilitate generating, maintaining, and/or updating amapping of wireless states and/or respectively associated wirelesstransition timers to a type of application, application data flow orbehavior, type of content, user behavior or activity in relation to theapplication or the UE, type of IP protocol, or other factors orparameters. The mapper component 412 can store the mapping in a timerlook-up table that can be generated or maintained by a look-up component414, wherein the timer look-up table can be stored in a data store 420.The transition management component 400 can contain an update component416 that can receive updates (e.g., information updates) relating tomodifications to wireless transition timers, changes in application dataflow, changes in user activity or behavior in relation to an applicationor the UE, modification of a defined state-switching-control criterion,modification of a defined state-switching-control protocol, modificationof a state-switching-control rule, etc. The mapper component 412 andupdate component 416 can operate to facilitate updating of the mappingrelating to wireless states and/or respectively associated wirelesstransition timers based at least in part on the updates, wherein theupdated mapping can be saved to the timer look-up table, which can bestored in the data store 420.

The transition management component 400 can comprise a processorcomponent 418 that can work in conjunction with the other components(e.g., monitor component 402, aggregator component 404, analyzercomponent 406, etc.) to facilitate performing the various functions ofthe transition management component 400. The processor component 418 canemploy one or more processors, microprocessors, or controllers that canprocess data, such as information relating to applications, users,wireless transition timers, wireless states, a mapping, mapper function,defined state-switching-control criterion, a definedstate-switching-control protocol, state-switching-control rules, and/orother information, to facilitate operation of the transition managementcomponent 400, as more fully disclosed herein, and control data flowbetween the transition management component 400 and other components(e.g., communication network, base station, an application, a server orother communication device, a cloud, etc.) associated with thetransition management component 400.

The transition management component 400 also can include a data store420 that can store data structures (e.g., user data, metadata), codestructure(s) (e.g., modules, objects, hashes, classes, procedures) orinstructions, information relating to applications, users, wirelesstransition timers, wireless states, a mapping, mapper function, definedstate-switching-control criterion, a defined state-switching-controlprotocol state-switching-control rules, and/or other information, tofacilitate controlling operations associated with the transitionmanagement component 400. In an aspect, the processor component 418 canbe functionally coupled (e.g., through a memory bus) to the data store420 in order to store and retrieve information desired to operate and/orconfer functionality, at least in part, to the monitor component 402,aggregator component 404, analyzer component 406, etc., and/orsubstantially any other operational aspects of the transition managementcomponent 400.

FIG. 5 illustrates a block diagram of an example communication network500 in accordance with various aspects and embodiments of the disclosedsubject matter. The communication network 500 can include a core network502 (e.g., mobile core network) that can facilitate communications byUEs wirelessly connected to the communication network 500. A UE can becommunicatively connected to the core network 502 via an AP (e.g., basestation). The core network 502 can facilitate wireless communication ofvoice and data associated with communication devices, such as UEs,associated with the communication network 500. The core network 502 canfacilitate routing voice and data communications between UEs and/orother communication devices (e.g., phone, computer, email server,multimedia server, audio server, video server, news server, financial orstock information server, other communication devices associated with anIP-based network 504 (e.g., the Internet), etc.) associated with thecommunication network 500. The core network 502 also can allocateresources to the UEs associated with the communication network 500 inthe communication network environment, convert or enforce protocols,establish and enforce QoS for the UEs, provide applications or servicesin the network, translate signals, and/or perform other desiredfunctions to facilitate system interoperability and communication in thewireless communication network. The core network 502 further can includedesired components, such as routers, nodes (e.g., general packet radioservice (GPRS) nodes, such as serving GPRS support node (SGSN), gatewayGPRS support node (GGSN), etc.), switches, interfaces, controllers,etc., that can facilitate communication of data between communicationdevices associated with the communication network 500.

The communication network 500 can include the IP-based network 504,which can facilitate communications by communication devices (e.g., UEs)that are connected to the communication network 500 via a wirelessconnection, or a wireline or landline connection. For example, a UE canbe communicatively connected to the IP-based network 504 via a wirelesscommunication connection with the core network 502, wherein the UE cancommunicate with other communication devices connected to thecommunication network 500. A UE can transmit messages, use applications,access or download content, etc., via the core network 502 and/or theIP-based network 504, or another communication network (not shown).

The communication network 500 can contain a transition controllercomponent 506 that can communicate (e.g., signal) with a UE tofacilitate the transition of the UE from one wireless state (e.g., DCHstate) to another wireless state (e.g., FACH state, Idle state, etc.).The transition controller component 506 also can track, and analyzeinformation relating to, resource usage by the communication network500, particularly the core network 502, in relation to servicing the UEor other UEs, wireless state transitions associated with the UE or otherUEs, wireless transition timers, user behavior or activity, applicationbehavior or activity, and/or other factors, to facilitate adjustingwireless transition timers and/or controlling wireless state transitionsfor the UE and other UEs to enhance the efficiency of UEs and thecommunication network. The transition controller component 506 canoperate in conjunction with an update component 508 to facilitateupdating information relating to wireless transition timers, wirelessstates, etc., for a UE. The update component 508 can facilitatetransmitting an update of information relating to wireless transitiontimers, wireless states, an associated mapping, etc., to a UE to updatea timer look-up table associated with the UE to facilitate modifyingwireless transition timers, wireless transitions, and/or an associatedmapping, etc., in relation to an application(s) used by the UE.

The communication network 500 also can include a processor component 510that can work in conjunction with (and/or be part of) the othercomponents (e.g., core network 502, IP-based network 504, transitioncontroller component 506, etc.) to facilitate performing the variousfunctions of the communication network 500. The processor component 510can employ one or more processors, microprocessors, or controllers thatcan process data, such as information relating to wireless or wirelinecommunications, applications, users, wireless transition timers,wireless states, a mapping, a mapper function, definedstate-switching-control criterion, a defined state-switching-controlprotocol, state-switching-control rules, and/or other information, tofacilitate operation of the communication network 500, as more fullydisclosed herein, and control data flow between the communicationnetwork 500 and other components (e.g., UE, base station, anapplication, a server or other communication device, a cloud, etc.)associated with the communication network 500.

The communication network 500 also can include a data store 512 that canstore data structures (e.g., user data, metadata), code structure(s)(e.g., modules, objects, hashes, classes, procedures) or instructions,information relating to wireless or wireline communications,applications, users, wireless transition timers, wireless states, amapping, a mapper function, defined state-switching-control criterion, adefined state-switching-control protocol state-switching-control rules,and/or other information, to facilitate controlling operationsassociated with the communication network 500. In an aspect, theprocessor component 510 can be functionally coupled (e.g., through amemory bus) to the data store 512 in order to store and retrieveinformation desired to operate and/or confer functionality, at least inpart, to the core network 502, IP-based network 504, transitioncontroller component 506, etc., and/or substantially any otheroperational aspects of the communication network 500.

FIG. 6 depicts a block diagram of an example UE 600 in accordance withan aspect of the disclosed subject matter. In an aspect, the UE 600 canbe a multimode access terminal, wherein a set of antennas 669 ₁-669 _(Q)(Q is a positive integer) can receive and transmit signal(s) from and towireless devices like access points, access terminals, wireless portsand routers, and so forth, that operate in a radio access network. Itshould be appreciated that antennas 669 ₁-669 _(Q) can be part of thecommunication platform 602, which can comprise electronic components andassociated circuitry that can provide for processing and manipulation ofreceived signal(s) and signal(s) to be transmitted, e.g., by receiversand transmitters 604, multiplexer/demultiplexer (mux/demux) component606, and modulation/demodulation (mod/demod) component 608.

In another aspect, the UE 600 can include a multimode operationchipset(s) 610 that can allow the UE 600 to operate in multiplecommunication modes in accordance with disparate technical specificationfor wireless technologies. In an aspect, multimode operation chipset(s)610 can utilize communication platform 602 in accordance with a specificmode of operation (e.g., voice, GPS). In another aspect, multimodeoperation chipset(s) 610 can be scheduled to operate concurrently (e.g.,when Q>1) in various modes or within a multitask paradigm.

In some implementations, the UE 600 can comprise an applicationcomponent 612 that can include one or more applications or canfacilitate using one or more applications. In accordance with variousimplementations, all or a portion of an application or thatapplication's functionality can reside on the UE 600 and/or all or aportion of that application or its functionality can reside on anotherdevice (e.g., another communication device, a communication devicelocated in or associated with a cloud, etc.) associated with thecommunication network.

In certain implementations, the UE 600 can include a transitionmanagement component 614 that can perform various functions andoperations to facilitate controlling setting or selecting of wirelesstransition timers, switching of the UE 600 between wireless states, etc.As more fully disclosed herein, the transition management component 614can identify a wireless state the UE 600 is to be in at a given time,and can control selecting or setting of wireless transition timers andtransitioning the UE 600 between various available wireless states(e.g., Idle state, URA state, FACH state, DCH state, etc.) at respectivetimes, based at least in part on the mapping relating to wirelesstransition timers and wireless states, in accordance with one or moredefined state-switching-control criterion and associated definedstate-switching-control protocol (and/or correspondingstate-switching-control rules).

In still another aspect, the UE 600 also can include a processor(s) 616that can be configured to confer functionality, at least in part, tosubstantially any electronic component within the UE 600, in accordancewith aspects of the disclosed subject matter. The processor(s) 616 canfacilitate enabling the UE 600 to process data (e.g., symbols, bits, orchips) for multiplexing/demultiplexing, modulation/demodulation, such asimplementing direct and inverse fast Fourier transforms, selection ofmodulation rates, selection of data packet formats, inter-packet times,etc. The processor(s) 616 also can facilitate enabling the UE 600 toprocess data relating to messaging, voice calls, applications, services(e.g., Internet services or access, services related to applications,etc.), wireless transition timers, wireless states, a mapping, a mapperfunction, a timer look-up table, defined state-switching-controlcriterion, a defined state-switching-control protocol,state-switching-control rules, etc. In accordance with variousimplementations, the processor(s) can facilitate identifying a wirelessstate the UE is to be in at a given time, and can facilitate controllingselecting or setting of wireless transition timers and/or transitioningthe UE 600 between various available wireless states (e.g., Idle state,URA state, FACH state, DCH state, etc.) at respective times.

The UE 600 also can contain a data store 618 that can store datastructures (e.g., user data, metadata); code structures (e.g., modules,objects, classes, procedures) or instructions; message hashes;information relating to applications, wireless transition timers,wireless states, a mapping, mapper function, a timer look-up table,defined state-switching-control criterion, a definedstate-switching-control protocol, state-switching-control rules, and/orother information; user policies; network or device information likepolicies and specifications; attachment protocols; code sequences forscrambling, spreading and pilot (e.g., reference signal(s))transmission; frequency offsets; cell IDs; encoding algorithms;compression algorithms; decoding algorithms; decompression algorithms;etc. In an aspect, the processor(s) 616 can be functionally coupled(e.g., through a memory bus) to the data store 618 in order to store andretrieve information (e.g., data structures; code structures;instructions; algorithms; information relating to applications, wirelesstransition timers, wireless states, a mapping, a mapper function, atimer-look-up table, defined state-switching-control criterion, adefined state-switching-control protocol, state-switching-control rules,and/or other information; etc.) desired to operate and/or conferfunctionality, at least in part, to the communication platform 602,multimode operation chipset(s) 610, application(s) 612, transitionmanagement component 614, and/or substantially any other operationalaspects of the UE 600.

FIG. 7 illustrates a block diagram of an example AP 700 (e.g.,femtocell, picocell, macro base station, etc.) in accordance with anaspect of the disclosed subject matter. The AP 700 can receive andtransmit signal(s) from and to wireless devices like access points(e.g., femtocells, picocells, base stations, etc.), access terminals(e.g., UEs), wireless ports and routers, and the like, through a set ofantennas 769 ₁-769 _(N). In an aspect, the antennas 769 ₁-769 _(N) are apart of a communication platform 702, which comprises electroniccomponents and associated circuitry that can provide for processing andmanipulation of received signal(s) and signal(s) to be transmitted. Inan aspect, the communication platform 702 can include areceiver/transmitter 704 that can convert signal from analog to digitalupon reception, and from digital to analog upon transmission. Inaddition, receiver/transmitter 704 can divide a single data stream intomultiple, parallel data streams, or perform the reciprocal operation.

In an aspect, coupled to receiver/transmitter 704 can be amultiplexer/demultiplexer (mux/demux) 706 that can facilitatemanipulation of signal in time and frequency space. The mux/demux 706can multiplex information (e.g., data/traffic and control/signaling)according to various multiplexing schemes such as, for example, timedivision multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM), etc. In addition,mux/demux component 706 can scramble and spread information (e.g.,codes) according to substantially any code known in the art, e.g.,Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and soon. A modulator/demodulator (mod/demod) 708 also can be part of thecommunication platform 702, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

The AP 700 also can comprise a processor(s) 710 that can be configuredto confer and/or facilitate providing functionality, at least partially,to substantially any electronic component in or associated with the AP700. For instance, the processor(s) 710 can facilitate operations ondata (e.g., symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as effecting direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc., to facilitate between anassociated UE and the communication network.

In another aspect, the AP 700 can include a data store 712 that canstore data structures; code instructions; rate coding information;information relating to measurement of radio link quality or receptionof information related thereto; information relating to establishing acommunications connection between a communication device (e.g., UE) andother communication devices; system or device information like policiesand specifications; code sequences for scrambling; spreading and pilottransmission; floor plan configuration; access point deployment andfrequency plans; scheduling policies; and so on. The processor(s) 710can be coupled to the data store 712 in order to store and retrieveinformation (e.g., information relating to multiplexing/demultiplexingor modulation/demodulation, information relating to radio link levels,information relating to establishing communication connectionsassociated with a UE(s) served by the AP 700, etc.) desired to operateand/or confer functionality to the communication platform 702, and/orother operational components of AP 700.

The aforementioned systems and/or devices have been described withrespect to interaction between several components. It should beappreciated that such systems and components can include thosecomponents or sub-components specified therein, some of the specifiedcomponents or sub-components, and/or additional components.Sub-components could also be implemented as components communicativelycoupled to other components rather than included within parentcomponents. Further yet, one or more components and/or sub-componentsmay be combined into a single component providing aggregatefunctionality. The components may also interact with one or more othercomponents not specifically described herein for the sake of brevity,but known by those of skill in the art.

In view of the example systems and/or devices described herein, examplemethods that can be implemented in accordance with the disclosed subjectmatter can be further appreciated with reference to flowcharts in FIGS.8-11. For purposes of simplicity of explanation, example methodsdisclosed herein are presented and described as a series of acts;however, it is to be understood and appreciated that the disclosedsubject matter is not limited by the order of acts, as some acts mayoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, a method disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a method inaccordance with the subject specification. It should be furtherappreciated that the methods disclosed throughout the subjectspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methods to computersfor execution by a processor or for storage in a memory.

FIG. 8 illustrates a flow chart of an example method 800 for adaptivelycontrolling wireless transition timers associated with wireless statesin relation to use of applications by a UE in a communication network,in accordance with various aspects and embodiments. In accordance withvarious aspects, the method 800 can be utilized by, for example, atransition management component.

At 802, a wireless transition timer can be identified (e.g., adaptivelyidentified or adjusted), based at least in part on type of applicationor changes in application behavior, type of content associated with theapplication, user behavior or activity in relation to the application orUE, type of IP protocol, and/or other factors, for use in relation to anapplication associated with a UE during a communication session tofacilitate transitioning the UE between a first wireless state and asecond wireless state. The transition management component can identifyor adjust the wireless transition timer for use in relation to theapplication during the communication session to facilitate transitioningthe UE between the first wireless state (e.g., a relatively higher powerwireless state, such as the DCH state) and the second wireless state(e.g., a relatively lower power wireless state, such as the FACH stateor Idle state). For instance, the transition management component cananalyze a mapping between wireless transition timers (and/or associatedwireless states) and type of application or changes in applicationbehavior, type of content associated with the application, user behavioror activity in relation to the application or UE, type of IP protocol,and/or other factors, and can identify a desirable wireless transitiontimer based at least in part on the mapping. The transition managementcomponent also can identify one or more other wireless transition timersfor use in relation to the application during the communication sessionto facilitate transitioning the UE between available wireless states(e.g., Idle state, URA state, FACH state, DCH state, etc.).

At 804, transition of the UE between the first wireless state and thesecond wireless state can be controlled (e.g., adaptively controlled)based at least in part on the wireless transition timer. The transitionmanagement component can facilitate transitioning the UE between thefirst wireless state and the second wireless state based at least inpart on the wireless transition timer. For example, when the wirelesstransition timer elapses, or the amount of elapsed time exceeds theamount of time associated with the wireless transition timer, thetransition management component can facilitate transitioning the UE fromthe first wireless state to the second wireless state.

Referring next to FIG. 9, depicted is a flow chart of another examplemethod 900 for adaptively controlling wireless transition timersassociated with wireless states in relation to use of applications by aUE in a communication network, in accordance with various aspects andembodiments. In accordance with various aspects, the method 900 can beutilized by a transition management component, for example.

At 902, activity, behavior, and/or data flow associated with anapplication being used by a UE can be monitored. The transitionmanagement component can monitor activity, behavior, and/or data flowassociated with the application during a communication session involvingthe UE and the application.

At 904, a type of application, change in the activity, behavior, or dataflow associated with the application, a type of content, user behavioror activity in relation to the application or UE, type of IP protocol,and/or other application-related characteristics can be identified. Thetransition management component can analyze information relating to theactivity, behavior, and/or data flow associated with the application.Based at least in part on that analysis, the transition managementcomponent can identify the type of application, change in the activity,behavior, or data flow associated with the application, the type ofcontent, user behavior or activity in relation to the application or UE,type of IP protocol, and/or other application-related characteristics.

At 906, a mapping relating to the wireless transition timers andwireless states can be analyzed in relation to the type of application,change in the activity, behavior, or data flow associated with theapplication, the type of content, user behavior or activity in relationto the application or UE, type of IP protocol, and/or otherapplication-related characteristics. The transition management componentcan retrieve the mapping from a timer look-up table in a data storeassociated with the transition management component. The transitionmanagement component can analyze the mapping along with the informationrelating to the type of application, change in the activity, behavior,or data flow associated with the application, the type of content, userbehavior or activity in relation to the application or UE, type of IPprotocol, and/or other application-related characteristics.

At 908, one or more wireless transition timers can be identified for useby the UE in relation to the application during the communicationsession, based at least in part on that analysis of the mapping, tofacilitate controlling switching the UE between wireless states. Thetransition management component can identify one or more wirelesstransition timers respectively associated with one or more of thewireless states, based at least in part on the analysis of the mapping.For example, the transition management component can apply therespective items of information relating to the type of application,change in the activity, behavior, or data flow associated with theapplication, the type of content, user behavior or activity in relationto the application or UE, type of IP protocol, and/or otherapplication-related characteristics to generate a result from themapping identifying or indicating one or more wireless transition timersto use in relation to the application during the communication sessionto facilitate controlling switching the UE between wireless states atdesired (e.g., optimal or acceptable) times.

At 910, the one or more wireless transition timers can be set. Thetransition management component can set the one or more wirelesstransition timers identified from the mapping. At 912, the transitioning(e.g., switching) of the UE between wireless states can be controlledbased at least in part on the one or more wireless transition timers.The transition management component can control switching of the UEbetween wireless states based at least in part on the one or morewireless transition timers. For example, while the UE is in the DCHstate, the transition management component can monitor activity on theCell_DCH and a first wireless transition timer of the one or morewireless transition timers can be used to facilitate to determiningwhether to transition the UE from the DCH state to another wirelessstate (e.g., FACH state). If the transition management componentdetermines that there has been no activity or low activity on theCell_DCH for a period of time that indicates the amount of time of thefirst wireless transition timer has elapsed, the transition managementcomponent can determine that the UE is to be transitioned from the DCHstate to another wireless state (e.g., FACH state). The transitionmanagement component can transition the UE from the DCH state to theother wireless state, and the UE can switch from the Cell_DCH to adifferent communication connection or channel (e.g., Cell_FACH).

Turning to FIG. 10, illustrated is a flow chart of still another examplemethod 1000 for generating a mapping relating to wireless transitiontimers and wireless states to facilitate adaptively controlling wirelesstransition timers associated with wireless states in relation to use ofapplications by a UE in a communication network, in accordance withvarious aspects and embodiments. The method 1000 can be employed by atransition management component, for example.

At 1002, information indicating a relationship between wirelesstransition timers and a subset of factors relating to applications and aUE can be obtained. The transition management component can obtaininformation relating to wireless transition timers; wireless states;various types of applications; the effects of changes in the activity,behavior, or data flow associated with respective types of applicationsin relation to wireless transition timers and wireless states; varioustypes of content; the effects of user behavior or activity associatedwith respective applications or the UE in relation to wirelesstransition timers and wireless; the effects of other application-relatedcharacteristics; and/or IP protocols associated with communications bythe UE during use of the application. The transition managementcomponent can obtain all or a portion of such information frommonitoring or probing activity, behavior, or data flow associated withrespective applications and/or can receive all or a portion of suchinformation from the communication network.

At 1004, information relating to the wireless transition timers andwireless states, and the information indicating a relationship betweenwireless transition timers and the subset of factors relating toapplications and the UE can be analyzed. The transition managementcomponent can analyze the information relating to the wirelesstransition timers and wireless states, and the information indicatingthe relationship between wireless transition timers and the subset offactors relating to applications and the UE, and can apply one or moredefined state-switching-control criterion as part of the analysis.

At 1006, a mapping relating to wireless transition timers and wirelessstates can be generated based at least in part on the results of theanalysis, in accordance with the one or more definedstate-switching-control criterion. The transition management componentcan generate the mapping relating to wireless transition timers andwireless states, based at least in part on the results of the analysis,in accordance with the one or more defined state-switching-controlcriterion. The mapping generated by the transition management componentcan facilitate enabling improved (e.g., optimal, increased, etc.)efficiency in performance by the UE, applications, and the communicationnetwork, as more fully disclosed herein.

At 1008, the mapping can be stored, for example, in a timer look-uptable. The transition management component can be stored in the timerlook-up table, which can be stored in a data store associated with thetransition management component. When the UE is using a particularapplication, the transition management component can retrieve themapping from the timer look-up table. The transition managementcomponent can identify one or more wireless transition timers torespectively employ for one or more of the wireless states, based atleast in part on the mapping and information relating to the type ofapplication, change in the activity, behavior, or data flow associatedwith the application, the type of content associated with theapplication, user behavior or activity in relation to the application orUE, other application-related characteristics, and/or IP protocolsassociated with communications by the UE during use of the application.The transition management component can apply the one or more wirelesstransition timers to facilitate controlling switching the UE betweenwireless states during a communication session involving the UE andapplication.

FIG. 11 presents a flow chart of an example method 1100 for adaptivelycontrolling wireless transition timers associated with wireless statesand signaling (e.g., keep-alive messages) in relation to use ofapplications by a UE in a communication network to facilitatecontrolling resource usage associated with the UE, in accordance withvarious aspects and embodiments. The method 1100 can be employed by atransition management component, for example.

At 1102, activity, behavior, and/or data flow associated with anapplication being used by a UE, and/or activity or behavior of a UE userin relation to the application and UE, can be tracked over time (e.g.,over a defined time period). The transition management component canmonitor and track activity, behavior, and/or data flow associated withthe application, and/or activity or behavior of a UE user in relation tothe application and UE, during one or more communication sessionsinvolving the UE and the application. The application can employ astandard policy whereby the application sends keep-alive messages to thecommunication network at a standard frequency (e.g., every 5 seconds, inaccordance with the standard policy) to facilitate maintaining analways-on communication connection between the UE and the communicationnetwork.

At 1104, information relating to the tracked activity, behavior, and/ordata flow associated with the application, the tracked activity orbehavior of the UE user, and/or other information can be analyzed. Thetransition management component can analyze the tracked activity,behavior, and/or data flow associated with the application, the trackedactivity or behavior of the UE user in relation to the application andUE, and/or other information to facilitate determining whether thefrequency of sending keep-alive messages associated with the applicationis to be modified (e.g., reduced) and identifying one or more wirelesstransition timers to use during the communication session.

At 1106, based at least in part on the analysis results, it can bedetermined that the frequency of sending keep-alive messages from the UEto the communication network can be modified to reduce the frequency.The transition management component determine that the frequency ofsending keep-alive messages from the UE to the communication network canbe modified to reduce the frequency, based at least in part on theanalysis results. For example, the transition management component cananalyze the information and can determine that the application data flowbetween the UE and communication network is sufficiently low enoughand/or the user activity with the application is sufficiently low enoughthat it is not necessary to maintain the always-on connection at alltimes during the communication session, and can determine that thefrequency of sending keep-alive messages can be reduced (e.g., tofacilitate reducing resource usage), while still maintaining theintegrity associated with the always-on connection and performance ofthe application.

At 1108, the frequency of sending keep-alive messages from the UE to thecommunication network can be reduced. The transition managementcomponent can identify a new reduced frequency (e.g., every 2 minutes orother suitable frequency) of sending keep-alive messages from the UE tothe communication network that will suitably (e.g., optimally, mostefficiently, acceptably, etc.) reduce resource usage associated with theUE and/or the network, while still maintaining the integrity associatedwith the always-on connection and performance of the application.

The transition management component can facilitate reducing thefrequency of sending keep-alive messages by, for example, interceptingall or at least some of the keep-alive messages sent by the applicationbefore delivery to the network and storing those intercepted messages ina queue, wherein the transition management component can control thesending of the keep-alive messages (e.g., retrieved or released from thequeue) to the communication network at the new reduced frequency. Asanother example, the transition management component can allow akeep-alive message to be sent to the communication network, intercept asubset of keep-alive messages and discard them, and allow anotherkeep-alive message to be sent to the communication network such that theallowed keep-alive messages are sent to the communication network inaccordance with the new reduced frequency, wherein this process ofallowing some of the keep-alive messages and intercepting subsets ofkeep-alive messages in between the allowed keep-alive messages cancontinue during the communication session. In still another example, ifthe application is intelligent, adaptable, or programmable, thetransition management component can transmit an instruction or requestto have the application reduce the frequency of sending keep-alivemessages to the new reduced frequency.

At 1110, one or more wireless transition timers can be identified foruse by the UE in relation to the application during the communicationsession, based at least in part on the analysis. The transitionmanagement component can identify one or more wireless transition timersrespectively associated with one or more of the wireless states, basedat least in part on the analysis at operation 1104 as well as ananalysis of a mapping relating to wireless transition timers andwireless states. For instance, according to the analyses and mapping,the transition management component can identify a first subset ofwireless transition times based at least in part on identifying theapplication as a first type of application and/or identifying a firsttype of content associated with the application, and/or can identify asecond subset of wireless transition timers based at least in part onidentifying the application as a second type of application and/oridentifying a second type of content associated with the application.

At 1112, the transitioning (e.g., switching) of the UE between wirelessstates can be controlled, based at least in part on the one or morewireless transition timers. The transition management component cancontrol switching of the UE between wireless states based at least inpart on the one or more wireless transition timers as well as thesending of keep-alive messages at the new reduced frequency.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 12 and 13 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented. While the subject matter has been described above inthe general context of computer-executable instructions of a computerprogram that runs on a computer and/or computers, those skilled in theart will recognize that this disclosure also can or may be implementedin combination with other program modules. Generally, program modulesinclude routines, programs, components, data structures, etc. thatperform particular tasks and/or implement particular abstract datatypes. Moreover, those skilled in the art will appreciate that thedisclosed methods may be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, mini-computing devices, mainframe computers, as well aspersonal computers, hand-held computing devices (e.g., PDA, phone,electronic tablets or pads, etc.), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. However, some, if not all aspects ofthis disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

With reference to FIG. 12, a suitable environment 1200 for implementingvarious aspects of this disclosure includes a computer 1212. Thecomputer 1212 includes a processing unit 1214, a system memory 1216, anda system bus 1218. It is to be appreciated that the computer 1212 can beused in connection with implementing one or more of the systems orcomponents shown and described in connection with FIGS. 1-7, orotherwise described herein. The system bus 1218 couples systemcomponents including, but not limited to, the system memory 1216 to theprocessing unit 1214. The processing unit 1214 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as the processing unit 1214.

The system bus 1218 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1394), and SmallComputer Systems Interface (SCSI).

The system memory 1216 includes volatile memory 1220 and nonvolatilememory 1222. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1212, such as during start-up, is stored in nonvolatile memory 1222. Byway of illustration, and not limitation, nonvolatile memory 1222 caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable programmable ROM(EEPROM), flash memory, or nonvolatile random access memory (RAM) (e.g.,ferroelectric RAM (FeRAM)). Volatile memory 1220 includes random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), direct Rambus RAM (DRRAM), direct Rambus dynamic RAM (DRDRAM),and Rambus dynamic RAM.

Computer 1212 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 12 illustrates, forexample, a disk storage 1224. Disk storage 1224 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. The disk storage 1224 also can include storage media separatelyor in combination with other storage media including, but not limitedto, an optical disk drive such as a compact disk ROM device (CD-ROM), CDrecordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or adigital versatile disk ROM drive (DVD-ROM). To facilitate connection ofthe disk storage devices 1224 to the system bus 1218, a removable ornon-removable interface is typically used, such as interface 1226.

FIG. 12 also depicts software that acts as an intermediary between usersand the basic computer resources described in the suitable operatingenvironment 1200. Such software includes, for example, an operatingsystem 1228. Operating system 1228, which can be stored on disk storage1224, acts to control and allocate resources of the computer system1212. System applications 1230 take advantage of the management ofresources by operating system 1228 through program modules 1232 andprogram data 1234 stored, e.g., in system memory 1216 or on disk storage1224. It is to be appreciated that this disclosure can be implementedwith various operating systems or combinations of operating systems.

A user enters commands or information into the computer 1212 throughinput device(s) 1236. Input devices 1236 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 1214through the system bus 1218 via interface port(s) 1238. Interfaceport(s) 1238 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 1240 usesome of the same type of ports as input device(s) 1236. Thus, forexample, a USB port may be used to provide input to computer 1212, andto output information from computer 1212 to an output device 1240.Output adapter 1242 is provided to illustrate that there are some outputdevices 1240 like monitors, speakers, and printers, among other outputdevices 1240, which require special adapters. The output adapters 1242include, by way of illustration and not limitation, video and soundcards that provide a means of connection between the output device 1240and the system bus 1218. It should be noted that other devices and/orsystems of devices provide both input and output capabilities such asremote computer(s) 1244.

Computer 1212 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1244. The remote computer(s) 1244 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer1212. For purposes of brevity, only a memory storage device 1246 isillustrated with remote computer(s) 1244. Remote computer(s) 1244 islogically connected to computer 1212 through a network interface 1248and then physically connected via communication connection 1250. Networkinterface 1248 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN), wide-area networks (WAN), cellularnetworks, etc. LAN technologies include Fiber Distributed Data Interface(FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ringand the like. WAN technologies include, but are not limited to,point-to-point links, circuit switching networks like IntegratedServices Digital Networks (ISDN) and variations thereon, packetswitching networks, and Digital Subscriber Lines (DSL).

Communication connection(s) 1250 refers to the hardware/softwareemployed to connect the network interface 1248 to the bus 1218. Whilecommunication connection 1250 is shown for illustrative clarity insidecomputer 1212, it can also be external to computer 1212. Thehardware/software necessary for connection to the network interface 1248includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and Ethernet cards.

FIG. 13 is a schematic block diagram of a sample-computing environment1300 (e.g., computing system) with which the subject matter of thisdisclosure can interact. The system 1300 includes one or more client(s)1310. The client(s) 1310 can be hardware and/or software (e.g., threads,processes, computing devices). The system 1300 also includes one or moreserver(s) 1330. Thus, system 1300 can correspond to a two-tier clientserver model or a multi-tier model (e.g., client, middle tier server,data server), amongst other models. The server(s) 1330 can also behardware and/or software (e.g., threads, processes, computing devices).The servers 1330 can house threads to perform transformations byemploying this disclosure, for example. One possible communicationbetween a client 1310 and a server 1330 may be in the form of a datapacket transmitted between two or more computer processes.

The system 1300 includes a communication framework 1350 that can beemployed to facilitate communications between the client(s) 1310 and theserver(s) 1330. The client(s) 1310 are operatively connected to one ormore client data store(s) 1320 that can be employed to store informationlocal to the client(s) 1310. Similarly, the server(s) 1330 areoperatively connected to one or more server data store(s) 1340 that canbe employed to store information local to the servers 1330.

It is to be noted that aspects, features, and/or advantages of thedisclosed subject matter can be exploited in substantially any wirelesstelecommunication or radio technology, e.g., Wi-Fi; Bluetooth; WorldwideInteroperability for Microwave Access (WiMAX); Enhanced General PacketRadio Service (Enhanced GPRS); Third Generation Partnership Project(3GPP) Long Term Evolution (LTE); Third Generation Partnership Project 2(3GPP2) Ultra Mobile Broadband (UMB); 3GPP Universal MobileTelecommunication System (UMTS); High Speed Packet Access (HSPA); HighSpeed Downlink Packet Access (HSDPA); High Speed Uplink Packet Access(HSUPA); GSM (Global System for Mobile Communications) EDGE (EnhancedData Rates for GSM Evolution) Radio Access Network (GERAN); UMTSTerrestrial Radio Access Network (UTRAN); LTE Advanced (LTE-A); etc.Additionally, some or all of the aspects described herein can beexploited in legacy telecommunication technologies, e.g., GSM. Inaddition, mobile as well non-mobile networks (e.g., the Internet, dataservice network such as Internet protocol television (IPTV), etc.) canexploit aspects or features described herein.

Various aspects or features described herein can be implemented as amethod, apparatus, system, or article of manufacture using standardprogramming or engineering techniques. In addition, various aspects orfeatures disclosed in the subject specification can also be realizedthrough program modules that implement at least one or more of themethods disclosed herein, the program modules being stored in a memoryand executed by at least a processor. Other combinations of hardware andsoftware or hardware and firmware can enable or implement aspectsdescribed herein, including disclosed method(s). The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device, carrier, or storage media.For example, computer-readable storage media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips, etc.), optical discs (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD), etc.), smart cards, and memorydevices comprising volatile memory and/or non-volatile memory (e.g.,flash memory devices, such as, for example, card, stick, key drive,etc.), or the like. In accordance with various implementations,computer-readable storage media can be non-transitory computer-readablestorage media and/or a computer-readable storage device can comprisecomputer-readable storage media.

As it is employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Further, processors can exploit nano-scalearchitectures such as, but not limited to, molecular and quantum-dotbased transistors, switches and gates, in order to optimize space usageor enhance performance of user equipment. A processor may also beimplemented as a combination of computing processing units.

A processor can facilitate performing various types of operations, forexample, by executing computer-executable instructions, wherein theprocessor can directly perform operations, and/or the processor canindirectly perform operations, for example, by directing or controllingone or more other components to perform operations. In someimplementations, a memory can store computer-executable instructions,and a processor can be communicatively coupled to the memory, whereinthe processor can access or retrieve computer-executable instructionsfrom the memory and can facilitate execution of the computer-executableinstructions to perform operations.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component are utilized to refer to “memory components,” entitiesembodied in a “memory,” or components comprising a memory. It is to beappreciated that memory and/or memory components described herein can beeither volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

As used in this application, the terms “component”, “system”,“platform”, “framework”, “layer”, “interface”, “agent”, and the like,can refer to and/or can include a computer-related entity or an entityrelated to an operational machine with one or more specificfunctionalities. The entities disclosed herein can be either hardware, acombination of hardware and software, software, or software inexecution. For example, a component may be, but is not limited to being,a process running on a processor, a processor, an object, an executable,a thread of execution, a program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers.

In another example, respective components can execute from variouscomputer readable media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry, which is operated by asoftware or firmware application executed by a processor. In such acase, the processor can be internal or external to the apparatus and canexecute at least a part of the software or firmware application. As yetanother example, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,wherein the electronic components can include a processor or other meansto execute software or firmware that confers at least in part thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment” (UE), “mobile station,” “mobile,”“wireless device,” “wireless communication device,” “subscriberstation,” “subscriber equipment,” “access terminal,” “terminal,”“handset,” and similar terminology are used herein to refer to awireless device utilized by a subscriber or user of a wirelesscommunication service to receive or convey data, control, voice, video,sound, gaming, or substantially any data-stream or signaling-stream. Theforegoing terms are utilized interchangeably in the subjectspecification and related drawings. Likewise, the terms “access point”(AP), “base station,” “Node B,” “Evolved Node B” (eNode B or eNB), “HomeNode B” (HNB), “home access point” (HAP), and the like are utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“owner,” “agent,” and the like are employed interchangeably throughoutthe subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms), which can provide simulated vision,sound recognition and so forth.

As used herein, the terms “example,” “exemplary,” and/or “demonstrative”are utilized to mean serving as an example, instance, or illustration.For the avoidance of doubt, the subject matter disclosed herein is notlimited by such examples. In addition, any aspect or design describedherein as an “example,” “exemplary,” and/or “demonstrative” is notnecessarily to be construed as preferred or advantageous over otheraspects or designs, nor is it meant to preclude equivalent exemplarystructures and techniques known to those of ordinary skill in the art.Furthermore, to the extent that the terms “includes,” “has,” “contains,”and other similar words are used in either the detailed description orthe claims, such terms are intended to be inclusive, in a manner similarto the term “comprising” as an open transition word, without precludingany additional or other elements.

It is to be appreciated and understood that components (e.g.,communication device, UE, AP, communication network, application,transition management component, etc.), as described with regard to aparticular system or method, can include the same or similarfunctionality as respective components (e.g., respectively namedcomponents or similarly named components) as described with regard toother systems or methods disclosed herein.

What has been described above includes examples of systems and methodsthat provide advantages of the disclosed subject matter. It is, ofcourse, not possible to describe every conceivable combination ofcomponents or methods for purposes of describing the disclosed subjectmatter, but one of ordinary skill in the art may recognize that manyfurther combinations and permutations of the disclosed subject matterare possible. Furthermore, to the extent that the terms “includes,”“has,” “possesses,” and the like are used in the detailed description,claims, appendices and drawings such terms are intended to be inclusivein a manner similar to the term “comprising” as “comprising” isinterpreted when employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: controlling, by a systemcomprising a processor, switching operation of a device between wirelessstates based on first information relating to a predictive usage of awireless resource by an application utilized by the device; anddetermining, by the system, a wireless transition timer based on secondinformation relating to activity associated with the application,wherein the wireless transition timer is associated with a wirelessstate of the wireless states.
 2. The method of claim 1, wherein thewireless transition timer indicates an amount of time that the device isto operate in the wireless state.
 3. The method of claim 1, furthercomprising: determining, by the system, the predictive usage of thewireless resource by the application based on third information relatingto wireless resource usage specifications associated with theapplication.
 4. The method of claim 3, wherein the wireless transitiontimer is a first wireless transition timer, wherein the wireless stateis a first wireless state, wherein the wireless states comprise thefirst wireless state and a second wireless state, and wherein the methodfurther comprises: analyzing, by the system, the third informationrelating to the wireless resource usage specifications associated withthe application; and determining, by the system, wireless transitiontimers, comprising the first wireless transition timer and a secondwireless transition timer, based on a result of the analyzing, whereinthe first wireless transition timer is associated with a first amount oftime that the device is to operate in the first wireless state, andwherein the second wireless transition timer is associated with a secondamount of time that the device is to operate in the second wirelessstate.
 5. The method of claim 1, wherein the predictive usage of thewireless resource by the application utilized by the device is a firstpredictive usage of the wireless resource by a first applicationutilized by the device, and wherein the method further comprises:determining, by the system, the first predictive usage of the wirelessresource by the first application based on a first result of a firstanalyzing of third information relating to first wireless resource usagespecifications associated with the first application; and determining,by the system, a first group of wireless transition timers, comprisingthe first wireless transition timer, based on the first result.
 6. Themethod of claim 5, further comprising: determining, by the system, asecond predictive usage of the wireless resource by a second applicationutilized by the device based on a second result of a second analyzing offourth information relating to second wireless resource usagespecifications associated with the second application; and determining,by the system, a second group of wireless transition timers based on thesecond result, wherein the second group of wireless transition timers isdifferent from the first group of wireless transition timers.
 7. Themethod of claim 1, wherein the wireless transition timer is a firstwireless transition timer, wherein the determining the wirelesstransition timer further comprises determining the first wirelesstransition timer based on the second information and based on a mappingrelating to the wireless states and wireless transition timers withrespect to respective levels of the activity associated with theapplication, wherein wireless transition timers comprise the firstwireless transition timer and a second wireless transition timer, andwherein the method further comprises: replacing, by the system, thesecond wireless transition timer with the first wireless transitiontimer in response to determining that a change in the activityassociated with the application has occurred, wherein the respectivelevels of the activity comprise a first level of the activity and asecond level of the activity, and wherein the change in the activity isfrom the second level of the activity to the first level of theactivity.
 8. The method of claim 1, further comprising: generating, bythe system, a mapping relating to the wireless states and wirelesstransition timers, comprising the wireless transition timer, withrespect to the activity associated with the application, based on thefirst information, the second information, and third informationrelating to the wireless states and the wireless transition timers; andstoring, by the system, the mapping in a data store, wherein thedetermining of the wireless transition timer comprises determining thewireless transition timer based on the mapping and the secondinformation.
 9. The method of claim 8, further comprising: modifying, bythe system, the mapping to generate an updated mapping based on updateinformation relating to the mapping; and modifying, by the system, thewireless transition timer to an updated wireless transition timer basedon the updated mapping, wherein the controlling of the switching of theoperation of the device between the wireless states comprisescontrolling of the switching of the operation of the device between thewireless states based on the updated wireless transition timer.
 10. Asystem, comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: controlling a transition ofoperation of a device between wireless states based on first datarelating to a predicted usage of a wireless resource by an applicationassociated with the device; and determining a wireless transition timerbased on second data relating to activity associated with theapplication, wherein the wireless transition timer is associated with awireless state of the wireless states.
 11. The system of claim 10,wherein the wireless transition timer indicates an amount of time thatthe device is to operate in the wireless state.
 12. The system of claim10, wherein the operations further comprise: determining the predictedusage of the wireless resource by the application based on specificationdata relating to wireless resource usage associated with theapplication.
 13. The system of claim 12, wherein the wireless transitiontimer is a first wireless transition timer, wherein the wireless stateis a first wireless state, wherein the wireless states comprise thefirst wireless state and a second wireless state, and wherein theoperations further comprise: analyzing the specification data; anddetermining wireless transition timers, comprising the first wirelesstransition timer and a second wireless transition timer, based on aresult of the analyzing, wherein the first wireless transition timer isassociated with a first amount of time that the device is to operate inthe first wireless state, and wherein the second wireless transitiontimer is associated with a second amount of time that the device is tooperate in the second wireless state.
 14. The system of claim 10,wherein the predicted usage of the wireless resource by the applicationassociated with the device is a first predicted usage of the wirelessresource by a first application utilized by the device, and wherein theoperations further comprise: determining the first predicted usage ofthe wireless resource by the first application based on a first resultof a first analysis of first specification data relating to a firstwireless resource usage associated with the first application; anddetermining a first group of wireless transition timers, comprising thefirst wireless transition timer, based on the first result.
 15. Thesystem of claim 14, wherein the operations further comprise: determininga second predicted usage of the wireless resource by a secondapplication associated with the device based on a second result of asecond analysis of second specification data relating to a secondwireless resource usage associated with the second application; anddetermining a second group of wireless transition timers based on thesecond result, wherein the second group of wireless transition timers isdifferent from the first group of wireless transition timers.
 16. Thesystem of claim 10, wherein the wireless transition timer is a firstwireless transition timer, wherein the determining the wirelesstransition timer further comprises determining the first wirelesstransition timer based on the second data and based on a mappingrelating to the wireless states and wireless transition timers inconnection with respective amounts of the activity associated with theapplication, and wherein the operations further comprise: modifying thesecond wireless transition timer to generate the first wirelesstransition timer in response to determining that a change in theactivity associated with the application has occurred, wherein therespective amounts of the activity comprise a first amount of theactivity associated with the application and a second amount of theactivity associated with the application, and wherein the change in theactivity is from the second amount of the activity to the first amountof the activity.
 17. The system of claim 10, wherein the operationsfurther comprise: generating a mapping relating to the wireless statesand wireless transition timers, comprising the wireless transitiontimer, with respect to the activity associated with the application,based on the first data, the second data, and third data relating to thewireless states and the wireless transition timers; and storing themapping in a data store, wherein the determining of the wirelesstransition timer comprises determining the wireless transition timerbased on the mapping and the second data relating to the activityassociated with the application.
 18. The system of claim 17, wherein theoperations further comprise: modifying the mapping to generate anupdated mapping based on a result of an analysis of update data relatingto the mapping; and modifying the wireless transition timer to anupdated wireless transition timer based on the updated mapping, whereinthe controlling of the transition of the operation of the device betweenthe wireless states comprises controlling of the transition of theoperation of the device between the wireless states based on the updatedwireless transition timer.
 19. A machine-readable storage medium,comprising executable instructions that, when executed by a processor,facilitate performance of operations, comprising: managing transitioningoperation of a device between wireless communication states based onfirst information relating to a predictive usage of a wirelesscommunication resource by an application associated with the device; anddetermining a wireless transition timer based on second informationrelating to activity associated with the application, wherein thewireless transition timer is associated with a wireless state of thewireless states.
 20. The machine-readable storage medium of claim 19,wherein the operations further comprise: determining the predictiveusage of the wireless communication resource by the application based onthird information relating to wireless communication resource usagespecifications associated with the application.